From 053c423e0ae6edfbfdb328d99a6309e26e4eacdf Mon Sep 17 00:00:00 2001 From: =?utf8?q?IOhannes=20m=20zm=C3=B6lnig?= Date: Wed, 25 May 2016 15:47:11 +0200 Subject: [PATCH] Updated README.Debian to reflect package rename --- debian/README.Debian | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/debian/README.Debian b/debian/README.Debian index 5a76dcf3..fbce8631 100644 --- a/debian/README.Debian +++ b/debian/README.Debian @@ -28,7 +28,7 @@ If you are developing your own JUCE application, you are of course free to follow upstream's advice. Installing the following packages will give you the 'Projucer' as Debian packages while keeping your embedded-module-code workflow: - - introjucer (contains the Projucer) + - juce-tools (contains the Projucer) - juce-modules-source (contains the source-code for the JUCE modules) The 'Projucer' as shipped with Debian has the following modification regarding @@ -76,6 +76,6 @@ I usually prefix these flags with JUCE_ (e.g. "CPPFLAGS" becomes You could recreate the Makefiles by running the project's .jucer file through Debian's "Projucer" (the so-generated Makefiles allow both overriding of -*FLAGS and building verbosely), but adding 'introjucer' to the Build-Depends is +*FLAGS and building verbosely), but adding 'juce-tools' to the Build-Depends is probably an overkill. -- 2.30.2